| Acknowledge/ Return Address
|
The address to which a document
holder must return his acknowledgment of receipt and document.
|
| Acknowledgment of Distribution
Receipts
|
Displays the holders of copies
from whom no acknowledgments have been received.
|
| Actual End Date
|
The date a work order or work
task was completed.
|
| Actual Start Date
|
The date a work order or work
task commenced.
|
| Additional Code
|
A field to define an additional
number or code to describe a person, for example:
- Tax number
- Passport number
- Any other
attribute associated with the person
|
| Address Type
|
The type of address, for
example:
|
| Allocated Copy Type
|
Where a Master/Copy has been
requested, denotes which will be issued.
|
| Anticipated Return Date
|
The date a copy of a document is
expected to be returned.
|
| Application
|
A descriptive name for a software
application. For example, Microsoft Word.
|
| Approval of Items Required
|
A flag that can be set when
creating a Product Baseline. When not set, a baseline may be created that does
not include all items that form part of the baseline.
|
| Approval Status
|
The approval status of a work
order can be either:
|
| Approved By
|
The person approving an object.
|
| Associated Object Type
|
Attributes may be associated
with the following object types:
- Change Requests
- Deviations /
Waivers
- Documents
- Items
- Locations
- Modification
Orders
- Organizations
- Persons
- Projects
- Serial Item
- Virtual Items
- Work Orders
|
| Attribute Name
|
The name of a characteristic,
for example:
|
| Audit Date
|
The date when object data was
actioned.
|
| Audit Event
|
The type of action on an
AssetWise object, for example:
|
| Audit Person
|
The name of the person who
created or last updated data related to the object
|
| Author (Notes)
|
When a note is added to an
object, the author defaults to the user who is currently logged in.
|
| Base Unit
|
The unit of measure of a field,
for example:
- Pounds for mass
- Yard for length
|
| Batch Qty
|
The number of items in a batch.
|
| Build History
|
The flag is set by
AssetWise when there are build history
documents related to a physical item serial or batch number.
|
| Build or Buy (Physical Items)
|
The physical item class can be
one of the following:
- P - Procured:
items bought from manufacturers or suppliers
- F - Fabricated:
items built within the company
- S -
Subcontracted: items designed within the company but built by a subcontractor.
|
| Category (Change Requests)
|
Changes can be classified as
follows:
- Class
1 - Changes affecting the form fit and/or function of the concept
- Class
2 - Changes not affecting the form, fit and/or function of the
concept but which require document updates
- Class
3 - Corrections, such as spelling mistakes
Each class has a different Approval permission,
allowing different people to approve different classes of changes.
|
| Change No/Number
|
A number to identify a change
event.
|
| Change Pending (Document)
|
The Change Pending status is set
by
AssetWise when a document is defined as an
affected document on a change with the status
"Proposed".
You cannot update or set this status, but you can
use it in queries.
Default = No
|
| Change Pending (Physical Items)
|
The Change Pending status is set
by
AssetWise when a physical item is defined as
an affected physical item on a change with the status
"Proposed".
You cannot update or set this status, but you can
use it in queries.
Default = No
|
| Checked Out
|
The status indicates whether a
document has been checked out to a user for correction. Documents can only be
checked out if the document is not approved.
You cannot update or set this status, but you can
use it in queries.
Default = No
|
| Checkout Location
|
A folder location for a document
that is being checked out.
|
| Child Location
|
The description of a child
location.
|
| Class (Physical and Virtual
Items)
|
The Category, Family Group, and
Style classify the item (physical or virtual) into groups that simplify the
search for groups of items
The Class must exist before it can be used as an
attribute to classify an object.
|
| Class (Product Structure Types)
|
Indicates the document class used
for physical item and serial item structures
|
| Class Type (Document Types)
|
The Type of document class, for
example:
- User-defined
- Item baseline
- Product baseline
- Virtual Item
baseline
- Virtual Item
structure
Many user-defined types can be added, but only
one item baseline type, one product baseline, one virtual item baseline and one
virtual item structure type can be added.
|
| Code (Item Types)
|
A single character shortcut code
for an item type.
|
| Code (Organizations)
|
An organization unit code. Refer
to
Organization Code.
|
| Code (Projects)
|
A project code.
|
| Config (Change Controlled for
Attributes)
|
Indicates whether the attribute
associated with a document or physical item may only be changed via a change
request.
|
| Configuration Item (CI)
|
Indicates whether a physical
item is a configuration item or not. This flag is used to differentiate between
configuration items and non-configuration items.
Configuration item attributes cannot be changed
without raising a change request.
If the Configuration Item flag is set, the
following field is applicable:
- Version – A
physical item is declared a CI when at least one of the following is true or is
needed for the entity when you, as the authority responsible for designing,
manufacturing, installing and/or supporting the item, are in a position to
control:
- The functional
characteristics and/or interfaces of the item and thus the changing of data and
documents which describe the item's configuration and application, and/or
- The physical
characteristics and/or interfaces of the item and thus the changing of data and
documents, which describe the item's configuration and application.
|
| Confirm Password
|
Confirmation of a password.
|
| Copy Issued To
|
The person to whom a copy of a
document has been issued.
|
| Copy Mask
|
Used to define the structure of
the copy number when automatic creation of copy numbers is enabled, for
example, #### results in copy numbers starting at 0001.
|
| Copy Number
|
A unique number or code to
identify each copy of a document.
|
| Copy Type
|
The type of copy can be one of
the following:
- Master -– the
singular source from which copies are made.
- Secondary
Master – a copy of the master acting as the master (when the master
is not available).
- Copy – a
duplicate of the master document.
|
| Create / Fill
|
A flag to create and fill a
transmittal form.
|
| Created (By)
|
The user who created an object.
|
| Cross-reference Number
(Documents)
|
An alternative number for a
defined document primary number, such as a different number can be allocated
for an existing document. This enables users to reference different numbers for
an existing document. For example, users can cross-reference an existing
document number, numbered to their own convention, to an ISBN number, or to a
supplier’s number.
|
| Cross-reference Number (Items)
|
An alternative number for a
defined physical item primary number. This enables users to reference different
numbers for an existing physical item, e.g. users can cross-reference an
existing physical item primary number to a NATO item number.
|
| Cross-reference Type
|
The description of a
cross-reference, for example:
- ISBN
- NATO Number
- Old Number
|
| Data Source
|
The name or description of a
database that is accessed.
|
| Database
|
A SQL Server or Oracle managed
relational database.
|
| Database Password
|
The password of a database user.
|
| Database User
|
The name of a database user.
|
| Date Acknowledged
|
Date acknowledged.
|
| Date Added
|
The date an object was added to
the database.
|
| Date Circulated
|
The date a document copy was
circulated to the circulation list.
|
| Date Created
|
The date a note was created.
|
| Date Implemented
|
The date a modification was
implemented.
|
| Date Issued
|
The date a document copy was
issued. Provided by the system and only visible from a report.
|
| Date Last Actioned
|
The date of the last action
taken on the object.
|
| Date Last Notified
|
The date the holder was last
notified of any changes.
|
| Date Obsolete (Document Class)
|
The date on which a document
class expires. An expired document class may not be used when adding a new
document or when updating an existing document with the expired document type.
|
| Date Obsolete (Documents)
|
The date from which the document
is obsolete.
|
| Date Obsolete (Items)
|
The date from which a physical
item is obsolete and is no longer available.
|
| Date Planned
|
The date a modification is
planned to be implemented.
|
| Date Received
|
The date a requisition for
copies was received.
|
| Date Registered
|
The date when a change or
modification was registered.
|
| Date Required
|
The date by which a copy of a
document is required.
|
| Date Returned
|
The date when a holder returned
his/her document copy.
|
| Date to Return
|
The date when a holder must
return a document copy.
|
| Date Security Expires
|
(Not Used. This is a legacy
field.)
|
| Days between Password Change
|
The number of days between
password changes.
|
| Decimals
|
Indicates the number of decimal
places in Number type fields.
|
| Default Address (Distribution)
|
A default Directory address for
the
"issuing" organization on Requisition Orders
|
| Default Approval Responsibility
|
The responsibility type for
approval of items and documents, for example,
"Design Authority".
|
| Default Media Type
|
The default media when creating
copies, for example,
"Paper".
|
| Default Organization
(Distribution)
|
Default
"issuing" Organization for Requisition Orders.
|
| Default Remarks Printed on
Distribution Transmittals
|
The message that is to be
printed on a transmittal by default.
|
| Description (Address Types)
|
A descriptive name to identify
the various address types, for example:
- Home Address
- Company Address
|
| Description (Change Request
Priorities)
|
The description of a change
request priority, for example:
|
| Description (Change Requests)
|
A short description of what is
changing on a change request.
|
| Description (Class)
|
The description of the class
used for item classification.
|
| Description (Cross-reference
Types)
|
The description of a
cross-reference type, for example:
|
| Description (Deviations &
Waivers)
|
A short description of a
deviation / waiver.
|
| Description (Item Link Type)
|
Item link types are names for
the relationship between two physical items, for example:
- Tools
- Jigs
- Test equipment
For a physical item, a tools relationship may be
defined to another physical item. The physical item is then related as a tool
of the first item.
This is not applicable to parent component
(child) relationships.
|
| Description (Item Type)
|
The description of an item type.
Refer to
Item Type.
|
| Description (Item)
|
A short description of a physical
item.
|
| Description (Location)
|
A short description of a
location.
|
| Description (Media Type)
|
The description of a document
media type, for example:
- Paper
- Electronic Source
Files (ESF)
- Microfiche
|
| Description (Modification
Priorities)
|
The description of a
modification priority, for example:
|
| Description (Modifications)
|
A short description of a
modification.
|
| Description (Note Priorities)
|
A description of a note
priority, for example:
- 1 - Urgent (1
Day processing)
- 9 - Routine (30
Day processing)
|
| Description (Number Types)
|
A descriptive name to identify
the various number types for directory entries for persons and organizations,
for example:
|
| Description (Organization
Relationship Types)
|
A description of the relationship
between two organizational units, for example:
|
| Description (Product Structure
Types)
|
A description of the product
structure type, for example:
- Maintenance
structure
- Product breakdown
structure
|
| Description (Project)
|
The description or name of a
project.
|
| Description (Responsibility
Type)
|
The description of a
responsibility type. For example,
"Design Authority",
"Author" and
"Approved By" responsibility types might be
defined.
|
| Description (Security
Classification)
|
The description of the relevant
security classification, for example:
|
| Description (Skills)
|
The description of a skill, for
example:
- Personal assistant
- Engineer
|
| Description (Units of Measure)
|
The description of the unit in
which an item is measured. For example, yards, litres, pounds and kilograms.
Refer to
UOM.
|
| Description (Virtual Items)
|
The description of a virtual
item.
|
| Description (Work Order
Priorities)
|
A description of a work
priority, for example:
- 1 - Urgent (1
Day processing)
- 9 - Routine (30
Day processing)
|
| Description (Work Order Types)
|
The description of a work order
type, for eample:
- Document Review
- Change Approval
|
| Description (Work Order)
|
The description of a work order.
|
| Description (Work Task)
|
The description of a task.
|
| Destroy Copies on Receipt
|
When set, copies that are
returned may be destroyed.
|
| Dev/Waiv Number
|
A unique number to identify a
deviation or waiver.
|
| Deviating Document
|
A document that may be linked to
a deviation or waiver.
|
| Deviating Physical Item
|
The end item product against
which a deviation or waiver is occurring.
|
| Directory Entries
|
A list of valid address names as
defined in the Address Types window, for example:
- Physical Home
Address
- Postal Home
Address
- Company E-mail
Address
|
| Directory Entry Type for E-Mail
|
Specifies the default address
type to use for e-mail, for example,
"Business".
|
| Distribution/ Notification
Address
|
The address to which a document
and notification notices are to be sent.
|
| Document Links
|
A name describing the
relationship between two documents. The following relationship types are
allowed:
- Propagated From
– a component document originated from the parent document.
- Propagated To –
a component document(s) that were originated from the parent document.
- Referenced By –
the parent document is referenced by the component documents.
- Referenced To –
the component document(s) that reference the parent document.
|
| Effective Date
|
The date from which a document
becomes effective.
|
| Enable E-Mail
|
When marked, allows notes and
work orders to be distributed by email.
|
| Exclude Non-Returnable Copies
|
When retrieving documents due to
be returned, acknowledged or notified, excludes non-returnable copies.
|
| Expiry Date (Unit of Measure)
|
The date on which a unit of
measure expires. Expired units of measure may not be used to define physical
items after the expiry date.
|
| Explode
|
The explode code can be
Yes or
No. This code is used for material
requirement planning.
When the explode code is
Yes and material requirement calculation
is done, the requirement is cascaded to the level where a
No explode code is encountered in the
given structure.
Default = Yes
|
| Extended Description
|
The Extended Description field
can be used for describing a physical item or a virtual item within a group in
more detail.
|
| First Name
|
The first name of a person.
|
| Fixed Value
|
The description of a fixed value
Attribute. A Lookup table must accompany this attribute type.
|
| Full Names
|
The full names of a person.
|
| Grace Logins
|
The number of times a user may
login after the password has expired.
|
| Group Name
|
The identification number or
code of a user group.
|
| Group Virtual Item
|
The prefix for a document that represents a group
virtual item. Together with the middle, revision and document type assigned to
group virtual items, constitutes a Group Virtual Item.
|
| Implemented Status
|
The status for modifications.
- Not Started
- WIP (Work In
Progress)
- Completed
|
| Initials
|
The initials of a person.
|
| Instruction
|
Description of work to be
performed.
|
| Issue To
|
The code of the person to whom a
document is issued.
|
| Issued By
|
The code of the person who
issued a document copy. Defaults to the user who created the transmittal, and
is only visible on the transmittal report
|
| Item Number
|
A number assigned to a physical
item. The item number and version combination must be unique in
AssetWise.
|
| Item type
|
A unique identifier that denotes
an item type. Examples of item types are:
- Preferred Item
- Standard Item
Item types are defined in a master table and must
exist before an item with the specific item type can be added.
|
| Keyword Class
|
A group name for a group of
keywords It enables grouping of keywords to simplify a keyword search.
|
| Keyword(s)
|
A descriptive word(s) to
describe an object. Used to facilitate searches.
|
| Latest Approved
|
The latest approved revision of a
document. A newer revision may be available but has not been approved yet.
|
| Latest Revision
|
The latest revision of a
document.
AssetWise only allows one document with the
same Prefix and Middle as the latest, or current, revision.
AssetWise resets the current revision flag
of the previous revision when a new document revision is added.
|
| Line No. (Distribution List)
|
A unique number identifying the
line number of a document on a document requisition.
|
| Line No. (Lists)
|
A unique number for each item on
a list, for example, a parts list. May be reordered to group like items, for
example, connectors.
|
| List Name
|
The name of a distribution list
as defined in the Distribution Lists window. Distribution lists are used to
distribute or to circulate a document(s) to a number of persons.
|
| Location
|
The location or position where
an object can be found. For example, a document’s location may be given as
cabinet A, drawer 2, Section 3.
|
| Location Code
|
A short code to identify a
location, e.g.
C43 to identify
Cabinet C, Drawer 4, Section 3.
|
| Location Type
|
The type of location as defined
in the Location Types window. Examples of location types are:
- Physical Item
Warehouse
- Document Filing
Depository
- Geographical
Breakdown
|
| Main Equipment
|
This flag is set if a physical
item is defined as the main equipment (for example, the end-product).
Default = No
|
| Mandatory
|
This field identifies whether a
characteristic is a required field. If a characteristic has been flagged as
Mandatory, the object cannot be approved until that field has been completed.
|
| Manufacturer Reference
|
The manufacturer's reference
number for a physical item.
|
| Mask
|
When creating multiple copies or
serial numbers, a mask specifies the format for the number (e.g. ####).
|
| Media
|
The media of a document copy,
for example, electronic source, paper or microfiche. Refer to
Description (Document
Media Type).
|
| Media ID
|
A unique identifying letter or
number to identify a document’s media. Refer to
Media.
|
| Middle (Document Number)
|
A document number is divided
into three parts. The Middle is the second part of the document number. Refer
to Prefix and Revision. A document is uniquely defined by the Prefix, Middle
and Revision combination, which means that
AssetWise will disallow two documents with
the same Prefix, Middle and Revision combination.
|
| Mime type
|
The last three characters of a
file name (such as .DOC or .XLS). The extension is used to locate the registry
entry to launch the appropriate application.
|
| Modification No.
|
A unique number identifying a
modification.
|
| Multiple Copies
|
When marked, allows creation of
multiple copies of a document.
|
| Multiple Serial Numbers
|
When marked, allows creation of
multiple serial numbers for an item.
|
| Name (Organizations)
|
The name of an organization
unit.
|
| National ID
|
The national identification
number for a person.
|
| New Baseline Document Prefix
|
The prefix for a document when
creating a baseline.
|
| New Password
|
New password for a user. See
Old password.
|
| No Longer Required
|
Indication that a document on a
requisition is no longer required.
|
| Note
|
Details of a note.
|
| Note Priority
|
Priority of a note.
|
| Note title
|
A short subject heading for a
note.
|
| Notification Address
|
The address to which
notifications for distributed documents are to be sent.
|
| Notifications to be Sent
|
Displays a list of holders to be
notified of changes to documents they hold.
|
| Notify
|
A flag to indicate whether to
notify holders of a document of any changes to the document they holds.
|
| Notify (Distribution Reasons)
|
Sets the default for the
notification of changes to a document per distribution reason. The default acts
as a guide and can be changed when issuing documents.
Default = Yes
|
| Old Password
|
Password a user wants to, or has
to, change.
|
| On Backorder
|
When a person has requested a
master of a document that is not available, the document is placed on
backorder.
|
| Organization / Organization Code
|
A short descriptive code to
uniquely identify an organization unit.
|
| Outstanding Circulated Copies
|
This flag enables a search for
all outstanding copies not yet returned. The flag is a three-stage flag,
covering a search for all outstanding copies, all circulation events or all
returned copies.
|
| Outstanding Copies are Overdue
|
Displays only outstanding copies
not yet received from the holders.
|
| Owner Project
|
The project primarily responsible
for creating, using and/or maintaining a document, physical item or virtual
item group.
|
| Password
|
A user-defined secret word for
gaining access to
AssetWise.
|
| Permission (Attributes)
|
A flag to identify attributes
that may only be changed by selected persons defined in Security.
|
| Person / Person Code
|
A code uniquely identifying each
person.
|
| Person's Remarks
|
Additional comment field for the
relation between a person and an organizational unit.
|
| Person's Role
|
The role of a person in relation
to the related organization unit, for example:
- Director
- Software designer
- Technical author
|
| Planned Duration
|
The estimated duration (number of
days) that a work order or task is expected to take.
|
| Planned End Date
|
The date by which a work order
or task is expected to be completed.
|
| Planned Start Date
|
The date by which a work order or
task is expected to commence.
|
| Position
|
The position of a component
relative to its immediate parent physical item. For example, the position of a
10 kilo-ohm resistor, of which there are three in a parent circuit assembly,
could be designated as R1, R15 and R22, relative to that specific circuit
assembly.
|
| Possible Conflict
|
Flagged when a document is
requested that may not be available.
|
| Preferred Copy No.
|
The copy number that is to be
used when distributing copies to a named person on a distribution list.
|
| Prefix (Document Number)
|
A document number is divided into
three parts. The Prefix is the first part of the document number. Refer to
Middle and Revision. A document is uniquely defined by the Prefix, Middle and
Revision combination, which means that
AssetWise will disallow two documents with
the same Prefix, Middle and Revision combination.
|
| Priority (Change Requests)
|
A priority designation,
indicating the urgency of a change request. The priority is selected from a
drop-down list. The list contains the priorities as defined in the Work Order
Priorities window.
|
| Priority (Deviations &
Waivers)
|
Deviations and Waivers are
classified as:
|
| Priority (Modifications)
|
A priority designation,
indicating the urgency of a modification.
|
| Priority (Notes)
|
A number to indicate the
priority of a note, with 0 being the highest priority.
|
| Priority (Work Orders)
|
A number to indicate the priority
of a work order, with 0 being the highest priority.
|
| Product Link Type
|
The type of link between items,
for example, test equipment.
|
| Product Structure Type
|
A descriptive name to
differentiate between various types of breakdown structures. For example:
- Production
Breakdown Structure
- Maintenance
Breakdown Structure
This enables users to define different types of
structures (or views of the physical item) for a physical item.
|
| Project Code
|
A unique identifying code for a
project.
|
| Qty (Copies)
|
The number of copies that are to
be created when adding multiple copies.
|
| Qty per
|
The quantity of a component
required by a parent physical item.
|
| Reason (Change Requests)
|
A description or justification
for a change request.
|
| Reason (Deviations &
Waivers)
|
A justification for a deviation
or waiver.
|
| Reason (Document Distribution
Reasons)
|
A description of the reason for
distributing documents, for example:
- For Production
- For Information
|
| Reference No.
|
A free text field for entering
information for a component part on a list, for example, the reference number
used on an assembly drawing for the item.
|
| Registration Number
|
An organization’s registration
number.
|
| Related Item (Equivalents)
|
Where equivalency between two physical items is
defined, the
Related Item field is the item number of
the equivalent physical item.
|
| Related Item (Links)
|
The item number of a related
item.
|
| Relationship (Equivalents)
|
The relation between two items
can be defined as one of the following:
- Equal to (=)
- Similar (~)
- Smaller than
(<)
- Greater than
(>)
Refer to
Item Equivalents.
|
| Relationship Type
(Organizations)
|
A unique name describing the
relationship between two organization units.
|
| Remarks
|
Any additional comment can be
entered in this field.
|
| Requested By
|
The name of the person
requesting a change or modification or Deviation/ Waiver.
|
| Requisition Mask
|
The format for a requisition
number when auto-numbering is set (e.g. ## to constrain to 2 digits).
|
| Requisition Number
|
A unique number identifying a
document issue event.
|
| Responsibility Type
|
The responsibility of an
organization or a person within an organization to the selected object, for
example, Approver, Design Authority.
|
| Responsible Organization
|
The organization unit responsible
for a project or Work Task.
|
| Responsible Person
|
The person who is responsible for
the applicable responsibility related to an object
|
| Results (Search)
|
The results returned from a
database search.
|
| Retrieve 'Latest Approved'
Documents (by default)
|
This flag, if set, guarantees
that a user will always retrieve the latest approved documents only.
|
| Revision
|
The revision of a document
indicates how many iterations it has undergone to correct its data contents.
The latest approved revision of a document is
usually regarded as the valid and fit-for-use iteration of the document.
The revision is only applicable to documents
subject to change control. To step the revision of a document, a user must go
through the change process as described under the applicable heading.
|
| Root Organization
|
The overall parent for an
organization structure.
|
| Search Name
|
The name assigned to a saved
query.
|
| Security Ref Number
|
The reference number of a
person's security clearance.
|
| Serial/Batch No.
|
The serial or batch number for a
physical item.
|
| Serialized
|
Serial or batch numbers can only
be added for physical items flagged as Serialized.
Default = No
|
| Skill area
|
A user-definable field to specify
areas of expertise.
|
| Software
|
Indicates whether a physical item
is a software item.
Default = No
|
| Standard Report Heading
|
The heading that is to appear on
all reports, e.g. a company name.
|
| Start
|
The starting number for multiple
serial numbers and copy numbers.
|
| Status (Change Requests)
|
The status of a change request
can be one of the following:
- Draft
- Proposed
- Expedited
- Approved
- Rejected
- Completed
- Cancelled
Affected objects may be associated with the
change as long as the status of the change request is either
"Draft" or
"Proposed".
The following additional information is required
when the status of the change request is set to
"Expedited":
- Date Expedited
- Expedited By
- Reason Expedited
The following additional information is required
when the status of the change request is set to
"Approved":
- Date Approved
- Approved By
The following additional information is required
when the status of the change request is set to
"Rejected":
- Date Rejected
- Rejected By
- Reason Rejected
The following additional information is required
when the status of the change request is set to
"Cancelled":
- Date Cancelled
- Cancelled By
- Reason Cancelled
|
| Status (Copies)
|
The status of a copy can be one
of the following:
- Available
- Issued
- Lost
- Destroyed
- Reserved
Copy status can only be changed from
"Available" to either
"Lost" or
"Destroyed", or from
"Issued" to
"Lost" or
"Destroyed".
Copy status may not be changed between
"Available" and
"Issued". The
"Issued" status is set when the copy is
issued to a person.
"Reserved" indicates that the copy is due to
be distributed on a requisition.
|
| Status (Deviations / Waivers)
|
The status for a deviation /
waiver can be one of the following:
- Pending
- Not Approved
- Approved
- Cancelled
|
| Status (Documents)
|
The status of a physical item
can either be:
Metadata of a physical item may not be changed
without an approved change request, once the status of the physical item is
"Released".
Data such as manufacturer reference numbers also
may not be changed once the status of the physical item is
"Released".
|
| Status (Modifications)
|
The status for a modification
can be one of the following:
|
| Status (Organizations)
|
The status of an organization
can either be:
|
| Status (Persons)
|
The status of a person can
either be:
|
| Status (Projects)
|
The status for a requisition can
be one of the following:
- Approved
- Not Approved
- Submitted
- In Progress
- Complete
- Recall
- Closed
- Cancelled
|
| Status (Requisition Items)
|
The status for an item on a
requisition can be one of the following:
- Not Processed
- Allocated
- Placed On Back
Order
- Copy Creation
Required
- Allocation Pending
- Issued
- Not Required
- Lost / Destroyed
|
| Status (Serial Numbers)
|
The status for an item serial
number can be one of the following:
- Reserved
- Superseded
- Current
|
| Status (Users)
|
Users may either be:
|
| Structure
|
An organization related to a
parent organization.
|
| Subject to Change Control (CC)
|
Indicates that a document or
virtual item group is subject to change control. It means that, to update the
object or any of its attributes, a formal change procedure must be initiated
once the status of the object is
"Approved" or
"Released".
|
| Superseded
|
A flag to indicate if a document
has been superseded by another document.
You cannot update or set this flag, but you can
use the flag in queries.
Default = No
|
| Superseded By
|
If users want to discontinue the
use of a specific document type, they enter the new document type in the
Superseded By Type field.
The new document type must exist in the table
before the document type can be used in the
Superseded By Type field.
|
| Surname
|
The surname of a person.
|
| Synopsis
|
A short description of the
contents of a document.
|
| Task
|
The number of a specific task.
|
| Tax Registration Number
|
The registered tax number of an
organization.
|
| Template
|
This flag indicates that a work
order is a template, from which copies of the template can be created.
|
| Title (Documents)
|
A document title, heading or
name.
|
| Title (Person)
|
The title of a person.
|
| Total qty
|
The sum of item or serial
positions. The total may not exceed the quantity of the item.
|
| Type (Attributes)
|
The type of characteristic
distinguishes between the following field types:
- Character
- Number
- Date
- Memo
- Fixed Field
|
| Type (Deviations / Waivers)
|
Denotes whether a record being
added is:
|
| Under Change (Document)
|
The
"Under Change" flag is set by
AssetWise when a document is defined as an
affected document on a change request, with the status either
"Expedited" or
"Approved".
You cannot update or set this flag, but you can
use the flag in queries.
Default = No
|
| Under Change (Items)
|
The
"Under Change" flag is set by
AssetWise when a physical item is defined as
an affected physical item on a change request, with the status either
"Expedited" or
"Approved".
You cannot update or set this flag, but you can
use the flag in queries.
Default = No
|
| Under Modification
|
The
"Under Modification" flag is set by
AssetWise when an item serial number is
added as an object to the modification.
Default = No
|
| Unique Change Nos.
|
A system setting indicating
whether all change request numbers are to be unique.
|
| Units of Measure / UOM
|
The UOM is a user-defined
identification field identifying the unit in which a physical item is measured.
For example:
- YRD - Yards
- L - Litres
- Kg - Kilograms
Refer to
Description (Unit of Measure).
|
| User / User ID
|
The user identification code.
|
| Version (Items)
|
A variant of a physical item. The
version is used to differentiate between different variants of the same
physical item. Only applicable if the item is flagged as a Configuration Item.
|
| Via e-mail
|
Distribute an electronic file
via e-mail.
|
| Virtual Item Code
|
A unique code identifying a
virtual item.
|
| Virtual Item Group Document
|
A document number consisting of
Prefix, Middle, Revision, and document type for virtual item group documents.
|
| Work Order (WO) Status
|
The status of a work order can
be:
- Submitted
- Cancelled
- Completed
- Suspended
- Work in Progress
- Planned
|
| Work Order (WO) Name
|
A name identifying a work order.
|
| Work Order (WO) Number
|
A unique number identifying a
specific work order.
|
| Work Order (WO) Owner
|
The person who owns a work order
(and who is responsible for the task).
|
| Work Order (WO) Types
|
A user-definable attribute
describing different types of work order.
|
| Work Orders Mask
|
Format for work order numbers
when these are automatically assigned.
|
| Work Priority
|
Priority of a work order.
|
